Skip to content

Conversation

Zalathar
Copy link
Contributor

@Zalathar Zalathar commented Sep 29, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

hkBst and others added 10 commits September 24, 2025 15:18
…nethercote

improve diagnostics for empty attributes

Adds a note about them not having any effect. This was previously done for `feature` attributes but no other attributes. In [converting the `feature` parser](rust-lang#146652) I removed that note. This PR adds it back in and makes it so all attributes benefit from it.

Not blocked on rust-lang#146652, either can merge first
impl Ord for params and use unstable sort

AFAICT we are only sorting to find duplicates, so unstable sort should work fine, and maybe is a tiny bit faster?
…jdonszelmann

Use `Iterator::eq` and (dogfood) `eq_by` in compiler and library

Now that rust-lang#137122 has landed, we can replace stuff that looks like:
```rust
let a: &[T];
let b: &[T];
let eq = a.len() == b.len() && a.iter().zip(b).all(|(a,b)| a == b)
```
with the much simpler `a.iter().eq(b)`, without losing the perf benefit of the different-length-fast-path.
Also dogfooded `Iterator::eq_by` (cc rust-lang#64295 ) while I'm at it.

First commit (4d1b6fa) should be very straightforward to review, second one (049a460) is slightly more creative, but IMHO a nice cleanup.
…mease

Fix removed version numbers of `doc_auto_cfg` and `doc_cfg_hide`

Tracking issue: rust-lang#43781

The `doc_auto_cfg` and `doc_cfg_hide` features were removed in a recent nightly (by rust-lang#138907).
I believe that the rustc version numbers at which the features were declared to be removed were incorrect, however, and should both be "1.92" (±1). As evidence in favour of this, the error we get from using this was:

```text
error[E0557]: feature has been removed
  --> src/lib.rs:22:29
   |
22 | #![cfg_attr(docsrs, feature(doc_auto_cfg))]
   |                             ^^^^^^^^^^^^ feature has been removed
   |
   = note: removed in 1.58.0; see <rust-lang#138907> for more information
   = note: merged into `doc_cfg`
```

Note especially the "removed in 1.58" claim. Further evidence is found in the comment further up this file: https://github.com/rust-lang/rust/blob/4ffeda10e10d4fa0c8edbd0dd9642d8ae7d3e66e/compiler/rustc_feature/src/removed.rs#L49-L53

I've chosen 1.92 as that was the milestone which rust-lang#138907 was added to.

cc `@GuillaumeGomez`
add joboet to library review rotation

Reviewing feels like fun again...
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Sep 29, 2025
@Zalathar
Copy link
Contributor Author

Rollup of everything not in #147145.

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Sep 29, 2025

📌 Commit 82db672 has been approved by Zalathar

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 29, 2025
@bors
Copy link
Collaborator

bors commented Sep 29, 2025

⌛ Testing commit 82db672 with merge 21a13b8...

@bors
Copy link
Collaborator

bors commented Sep 29, 2025

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 21a13b8 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Sep 29, 2025
@bors bors merged commit 21a13b8 into rust-lang:master Sep 29, 2025
11 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Sep 29, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#146653 improve diagnostics for empty attributes 1d14c61677c25ed1ce05d1460b27ffdd93e49fce (link)
#146987 impl Ord for params and use unstable sort ba8f00d9c8f62c468d9e3afc4f48dff026e746da (link)
#147101 Use Iterator::eq and (dogfood) eq_by in compiler and li… 196d798afa1c6d8ef56fd0c50da732bfaafcebd6 (link)
#147123 Fix removed version numbers of doc_auto_cfg and `doc_cfg_… 69e8b5e177df0c8d4da415cd457f6f129a3da461 (link)
#147149 add joboet to library review rotation 3ac23352136cc99fd425c8ca6c40235197979e56 (link)

previous master: 128b36a4a4

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

Copy link
Contributor

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 128b36a (parent) -> 21a13b8 (this PR)

Test differences

Show 42 test diffs

42 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 21a13b8864a7dd614e9a96afd57b58c7fcf0bd6b --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-gnu-llvm-20-3: 5822.7s -> 6806.7s (16.9%)
  2. pr-check-1: 1756.3s -> 1572.4s (-10.5%)
  3. dist-aarch64-apple: 6370.0s -> 7029.4s (10.4%)
  4. aarch64-apple: 8299.6s -> 9081.0s (9.4%)
  5. x86_64-gnu-llvm-20-1: 3740.8s -> 3388.6s (-9.4%)
  6. i686-gnu-2: 6470.4s -> 5867.8s (-9.3%)
  7. dist-ohos-aarch64: 4209.0s -> 4596.6s (9.2%)
  8. x86_64-rust-for-linux: 2995.6s -> 3264.9s (9.0%)
  9. dist-riscv64-linux: 4938.6s -> 5381.4s (9.0%)
  10. aarch64-msvc-1: 6665.3s -> 7219.4s (8.3%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (21a13b8): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.2% [-0.2%, -0.2%] 1
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 7.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
7.3% [7.3%, 7.3%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 7.3% [7.3%, 7.3%] 1

Cycles

Results (secondary 2.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
2.7% [1.4%, 3.6%] 8
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
0.6% [0.3%, 1.0%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.2% [-0.2%, -0.2%] 3
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [-0.2%, 1.0%] 5

Bootstrap: 470.851s -> 470.943s (0.02%)
Artifact size: 387.67 MiB -> 387.66 MiB (-0.00%)

@Zalathar Zalathar deleted the rollup-w81rn0j branch September 29, 2025 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-attributes Area: Attributes (`#[…]`, `#![…]`) A-meta Area: Issues & PRs about the rust-lang/rust repository itself merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants